Codecov Report

Attention: Patch coverage is 50.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 48.08%. Comparing base (e9f1be2) to head (917cf55).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   46.23%   48.08%   +1.85%     
==========================================
  Files           5        6       +1     
  Lines         186      183       -3     
==========================================
+ Hits           86       88       +2     
+ Misses        100       95       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

I see what you mean. Just from the name "one hot" I would have thought things like having multiple ones and a single row or column would be forbidden (here I am referring to the example at that link). But apparently this is the usage in ML, and also one element is just a much clearer name.

I see what you mean. Just from the name "one hot" I would have thought things like having multiple ones and a single row or column would be forbidden (here I am referring to the example at that link). But apparently this is the usage in ML, and also one element is just a much clearer name.

They call that more general case a onehotbatch in OneHotArrays.jl, but still you can see the idea is to find the location of a value in a collection and use that to define a basis vector, so it is a very similar concept to how we use onehot but the application is a bit different. Anyway, I'll probably bring back onehot for backwards compatibility but deprecate it in favor of oneelement.